Skip to content

Conversation

@HofmeisterAn
Copy link
Collaborator

@HofmeisterAn HofmeisterAn commented Aug 9, 2025

While looking into the issue #11 (comment), I noticed the root cause seems to be related to this PR #6. After carefully reviewing the diff, I didn't see anything obviously wrong, so I started reverting a few changes. Thats when I noticed that using StringContent(string, Encoding?, string?) instead of JsonContent.Create(T, JsonSerializerOptions?) seems to fix the issue.

Im still not entirely sure if this fully resolves the issue or what the exact root cause is. Im trying to dig deeper. In the meantime, I'd like to open a PR so others can validate and test it.

My guess is that the problem lies somewhere internally in how JsonContent handles connections, possibly causing an incompatibility with Docker.DotNet's custom HTTP client.

Follow-ups

  • Add a GitHub workflow that runs tests against Podman (CI).

@HofmeisterAn HofmeisterAn added the bug Something isn't working label Aug 9, 2025
@HofmeisterAn HofmeisterAn merged commit aff1ec3 into main Aug 9, 2025
2 checks passed
@HofmeisterAn HofmeisterAn deleted the bugfix/return-string-instead-of-json-content branch August 9, 2025 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants